home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990422-19990725
/
000120_news@watsun.cc.columbia.edu _Mon May 31 18:23:37 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-07-23
|
3KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id SAA25347
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 31 May 1999 18:23:37 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id SAA16539
for kermit.misc@watsun.cc.columbia.edu; Mon, 31 May 1999 18:20:41 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: "Joe H. Gallagher" <dtrwiz@ix.netcom.com>
Subject: timing problems
Date: Mon, 31 May 1999 18:17:39 -0400
Organization: Netcom
Message-ID: <37530A82.194A@ix.netcom.com>
To: kermit.misc@watsun.cc.columbia.edu
Following is two examples of K95 script code which work on a
slower processor, but fail to work on a faster processor.
Example #1
Sending three <CR> to wake up a VAX thru a DECserver 700 to
start the login process.
The following code worked on a 175 Megahertz processor, but would
NOT work on a faster processor.
. . .
:LOOP1
clear
message {Requesting username prompt...}
output \13\13\13
input 2 Username:
if success goto HAVEUSERNAME
goto LOOP1
:HAVEUSERNAME
message {Logging in . . . }
output \%a\13 ; send username
output \%p\13 ; send password
The faster processor required code like:
. . .
:LOOP1
clear
message {Requesting username prompt...}
output \13
message {Synchronizing .}
output \13
message {Synchronizing . .}
output \13
message {Synchrohizing . . .}
input 2 Username:
if success goto HAVEUSERNAME
goto LOOP1
:HAVEUSERNAME
message {Logging in . . . }
output \%a\13 ; send username
output \%p\13 ; send password
Example 2.
A DATATRIEVE procedure VALIDATION is started on the VAX. The
KERMIT script is to wait until the procedure responds with a "Done".
The following code worked on a 175 Megahertz processor, but would
not work on a faster processor.
. . .
message {Analyzing claims . . .}
clear
output dtr execute validation\13
set count 180 ; 180 * 5 second / 60 second/min = 15 minutes
:Y1
message {Synchronizing with host during validation . . .}
input 5 Done
if success goto CONT3
reinput 0 CARRIER
if success goto ENDVAL
if count goto Y1
:ENDVAL
fatalerror {Verification never completed.}
:CONT3
. . .
On a faster processor, the script file would "hang" on the line
"input 5 Done". A reboot of the system was required to clear the
conditions. To get the code to work on a faster processor, adding
some commented likes caused the code to start working.
. . .
message {Analyzing claims . . .}
clear
output dtr execute validation\13
set count 180 ; 180 * 5 second / 60 second/min = 15 minutes
:Y1
message {Synchronizing with host during validation . . .}
;pause 1
;echo 1
;pause 1
;echo 2
;pause 1
;echo 3
;pause 1
;echo 4
;pause 1
;echo 5\13
input 5 Done
if success goto CONT3
reinput 0 CARRIER
if success goto ENDVAL
if count goto Y1
:ENDVAL
fatalerror {Verification never completed.}
:CONT3
. . .
Questions:
1. How does one write K95 scripts which are independent of
the speed of PC?
2. Which script commands are most likely to encounter timing or
processor speed problems?
3. Are these kinds of problems unique to the hardware I am using?
to K95? or to KERMIT scripts in general?